Require a database or secret on schema commands #498
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Ticket(s): FE-6215
Problem
fauna schema status
without specifying a database, secret or config/profile errors out.fauna schema status
does not accept adir
argument when it should.Solution
validateDatabaseOrSecret
check on the schema command.localSchemaOptions
in theschema status
options.Result
All schema commands will yell at you if you don't provide a database, secret or profile.
Testing
Added a test.